Method for reducing write barrier overhead

ABSTRACT

A computer system and method for compiling a program, where the program executes pointer assignments from a source object to a destination object, each source object being addressable through a first pointer and each destination object being addressable through a second pointer. The system and method eliminate write barrier code from association with compiled program code when the first pointer points to a source object whose type is prolific, eliminate write barrier code from association with compiled program code when the second pointer points to a destination object whose type is non-prolific, and associate write barrier code with compiled program code when the source object is non-prolific and the destination object is prolific. Additionally, the system and method can determine not to associate write barrier code with a compiled program code if the second pointer points to a destination object whose type is non-prolific and if the first pointer points to a source object whose type is prolific.

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application is based upon and claims priority from prior U.S. Provisional Patent Application No. 60/278,060, filed on Mar. 22, 2001, and further is based upon and claims priority from prior U.S. Provisional Patent Application No. 60/281,759, filed on Apr. 5, 2001, collectively the entire disclosure of which is herein incorporated by reference.

[0002] The present patent application is related to co-pending and commonly owned U.S. patent application Ser. No. ______, Attorney Docket No. YOR920010284US3, entitled “Method for Efficient Garbage Collection Based on Object Types”, filed on even date with the present patent application, the entire teachings of which being hereby incorporated by reference.

BACKGROUND OF THE INVENTION

[0003] 1. Field of the Invention

[0004] This invention generally relates to the field of automatic memory management, and more particularly relates to a system and method for reducing write barrier overhead.

[0005] 2. Description of Related Art

[0006] The popularity of object-oriented programming languages, such as the Java Programming Language, has rekindled a great deal of interest in automatic memory management. Java does not provide the programmer with an explicit mechanism to deallocate objects, and requires the underlying Java Virtual Machines (JVM) to support garbage collection. Researchers have developed a large number of garbage collection algorithms over the last four decades.

[0007] One of the popular approaches to garbage collection is known as generational garbage collection. It is inspired by an observation, known as the weak generational hypothesis, that most objects die young. A simple generational scheme involves partitioning the heap space into two regions—a nursery (or new generation) and an old generation. All new objects are allocated in the nursery. Most collections, termed minor collections, only reclaim garbage from the nursery. Survivors from a minor collection are promoted to the older generation, which is subjected to collection only during infrequent, major collections. In order to support a generational collection, the compiler has to insert a write barrier for each statement that writes into a pointer field of an object, to keep track of all pointers from objects in the old generation to objects in the nursery. These source objects in the old generation are added, as roots for minor collection, so that objects in the nursery that are reachable from those objects are not mistakenly collected. Compared with their non-generational counterparts, generational collectors typically have short pauses, due to the need to look at a smaller heap partition at a time, but lead to lower throughput of applications due to the overhead of executing write barriers.

[0008] Problems of the generational garbage collection scheme include:

[0009] Sub-optimal throughput of applications due to the overhead of executing write barriers.

[0010] The overhead of processing write buffer entries (created as a result of executing write barriers).

[0011] The overhead of examining reference fields in objects (to ensure that all references pointing into the region of the heap being collected are found).

[0012] The problems associated with premature promotion of young objects that are going to die soon anyway, such as executing more write barriers, dragging dead objects into the old generation, and requiring more major collections.

[0013] The overhead of promoting and scanning long-lived objects.

[0014] Therefore a need exists to overcome the problems with the prior art as discussed above, and particularly for a method of reducing write barrier overhead.

SUMMARY OF THE INVENTION

[0015] According to a preferred embodiment of the present invention, a system and method of compiling program, determine that a program code, at a point in a program, creates a reference from a source object to a destination object. The system and method then associate write barrier code with the program code if, at the point in the program, the source object is non-prolific and the destination object is prolific, and otherwise determine not to associate write barrier code with the program code.

[0016] According to a preferred embodiment of the present invention, wherein the program executes pointer assignment from the source object to the destination object, and wherein the source object being addressable through a first pointer and the destination object being addressable through a second pointer, the system and method determining not to associate write barrier code with the program code if at least one of the following:

[0017] the first pointer points to a source object whose type is prolific, and the second pointer points to an object whose type is non-prolific.

[0018] According to a preferred embodiment of the present invention, a system and method of compiling program are provided, where the program executes pointer assignments from a source object to a destination object, each source object being addressable through a first pointer and each destination object being addressable through a second pointer. The system and method comprise:

[0019] determining not to associate write barrier code with a compiled program code if the second pointer points to a destination object whose type is non-prolific.

[0020] According to a preferred embodiment, the system and method additionally may determine not to associate write barrier code with a compiled program code if the first pointer points to a source object whose type is prolific.

[0021] According to an alternative preferred embodiment of the present invention, a system and method of compiling program are provided, where the program executes pointer assignments from a source object to a destination object, each source object being addressable through a first pointer and each destination object being addressable through a second pointer. The system and method eliminate write barrier code from association with compiled program code when the first pointer points to a source object whose type is prolific.

[0022] Further, the system and method can eliminate write barrier code from association with compiled program code when the second pointer points to a destination object whose type is non-prolific.

[0023] Additionally, the system and method can associate write barrier code with compiled program code when the source object is non-prolific and the destination object is prolific.

BRIEF DESCRIPTION OF THE DRAWINGS

[0024]FIG. 1 is a block diagram illustrating a computer system in accordance with a preferred embodiment of the present invention.

[0025]FIG. 2 is a more detailed block diagram showing a garbage collecting application in the system of FIG. 1, according to a preferred embodiment of the present invention.

[0026]FIG. 3 is a more detailed block diagram of a data memory in the system of FIG. 1, according to a preferred embodiment of the present invention.

[0027]FIGS. 4, 5 and 6 are operational flow diagrams illustrating exemplary operational sequences for the system of FIG. 1, according to a preferred embodiment of the present invention.

[0028]FIG. 7 is a table of exemplary code segments for the system of FIG. 1, according to a preferred embodiment of the present invention.

DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0029] The present invention, according to a preferred embodiment, overcomes problems with the prior art by implementing a new approach to garbage collection based on the notion of prolific and non-prolific object types. Relatively few object types, referred to as prolific types, usually account for a large percentage of objects (and heap space) cumulatively allocated by the program. The objects of prolific types have short lifetimes, and therefore, account for a large percentage of garbage that is collectible at various points during program execution. The present invention, according to a preferred embodiment, presents a new approach to garbage collection that relies on finding garbage primarily among prolific objects. The present invention improves upon generational garbage collection by distinguishing between groups of objects based on type rather than age.

[0030] In a preferred embodiment of a type-based garbage collector, all objects of a prolific type are assigned at allocation time to a prolific space (P-space). All minor collections are performed on the P-space. All objects of a non-prolific type are allocated to a non-prolific space (NP-space). Unlike generational collection, objects are not “promoted” from the P-space to the NP-space after a minor collection. This approach leads to several benefits over generational collection:

[0031] It allows a compiler to identify and eliminate unnecessary write barriers using simple type checks. This leads to performance benefits like:

[0032] reduction in the direct overhead of executing write barriers; and

[0033] for some write barrier implementations, a reduction in the number of roots that are considered during minor collections, leading to fewer objects being scanned and potentially fewer collections.

[0034] It reduces the number of reference fields examined during garbage collection by using static type information to infer the direction of pointers.

[0035] It avoids the problems associated with premature promotion of young objects that are going to die soon anyway, such as executing more write barriers, dragging dead objects into the old generation, and requiring more major collections.

[0036] In a copying collector, the overhead of copying objects of non-prolific types across generations is avoided.

[0037] The term “prolific type” is used to refer to a type that has a sufficiently large number of instances. More specifically, a type may be prolific with respect to a program if, for example, the fraction of objects of this type exceeds a certain threshold. Preferably, the threshold is simply set to 1% of the total number of objects created by an application. This threshold can be adjusted to control the size of the P-space 308. All remaining types are referred to as non-prolific. Alternatively, prolific types may also be defined as some “k” popular types with respect to the total number of instances.

[0038] The objects of prolific types are expected to have small lifetimes. The present invention is based on the expectation that the objects of prolific types die younger than objects of non-prolific types. It follows that most of the garbage collectible at various stages of the application would consist of objects of prolific types. Accordingly, a preferred embodiment of the present invention is a different way of collecting garbage, which looks for garbage first among objects of prolific types.

[0039]FIGS. 1 and 2 illustrate an exemplary garbage collection system according to a preferred embodiment of the present invention. The garbage collection system 100 includes a computer system 101, having a garbage collector 120. The computer system 101, according to the present example, includes a controller/processor 122, which processes instructions, performs calculations, and manages the flow of information through the computer system 101. Additionally, the controller/processor 122 is communicatively coupled with program memory 110. Included within program memory 110 are a garbage collector 120 (which will be discussed in later in greater detail), operating system platform 116, Java Programming Language 114, Java Virtual Machine 112, glue software 118, Java application 204, a memory allocator 202, a compiler 206, and a type profiler 208. It should be noted that while the present invention is demonstrated using the Java Programming Language, it would be obvious to those of 110 ordinary skill in the art, in view of the present discussion, that alternative embodiments of the invention are not limited to a particular computer programming language. The operating system platform 116 manages resources, such as the data stored in data memory 124, the scheduling of tasks, and processes the operation of the garbage collector 120 in the program memory 110. The operating system platform 116 also manages a graphical display interface (not shown), a user input interface (not shown) that receives inputs from the keyboard 106 and the mouse 108, and communication network interfaces (not shown) for communicating with a network link (not shown). Additionally, the operating system platform 116 also manages many other basic tasks of the computer system 101 in a manner well known to those of ordinary skill in the art.

[0040] Glue software 118 may include drivers, stacks, and low level application programming interfaces (API's) and provides basic functional components for use by the operating system platform 116 and by compatible applications that run on the operating system platform 116 for managing communications with resources and processes in the computing system 101.

[0041] Each computer system 101 may include, inter alia, one or more computers and at least a computer readable medium 132. The computers preferably include means for reading and/or writing to the computer readable medium 132. The computer readable medium 132 allows a computer system 101 to read data, instructions, messages or message packets, and other computer readable information from the computer readable medium. The computer readable medium, for example, may include non-volatile memory, such as Floppy, ROM, Flash memory, disk drive memory, CD-ROM, and other permanent storage. It is useful, for example, for transporting information, such as data and computer instructions, between computer systems.

[0042]FIG. 3 illustrates a preferred embodiment of the data memory 124 of the garbage collecting system 100 of FIG. 1. Data memory 124 includes a write buffer 302, a type profile 304 containing information about types of objects, and a heap space 306 preferably divided into a prolific space 308 and a non-prolific space 310. Note, however, that the heap space 306, according to an alternative preferred embodiment, may combine both prolific and non-prolific object space into one combined memory space.

[0043] A preferred embodiment of the type-based approach in a Java Virtual Machine (JVM) 112 is now described. The JVM 112 supports a number of different garbage collectors 120, which can be used in different configurations.

[0044] The JVM 112 is enhanced to introduce two modes of execution. In one (profiling) mode, as shown in FIG. 4, the type profile 304 is collected; in the other (production) mode, as shown in FIG. 5, the type profile 304 collected in the profiling run 400 is used by the memory allocator 202 and by the garbage collector 120 to implement type-based heap management, and by the compiler 206 to optimize away redundant write barrier code.

[0045] In the profiling mode 400, the type profiler 208 monitors all allocation requests, collects its type profile, and produces a file (type profile 304) with the profile information, including class hierarchy information. In the production mode 500, the memory allocator 202, in step 504, uses the previously collected type profile 304 to make allocation decisions. Also, in the production mode, the garbage collector 120, at step 506, repeatedly collects space occupied by unreachable objects of prolific types. When a triggering event occurs, such as only freeing a small portion of memory, at step 508, it collects the entire heap in step 510.

[0046] The simplest method of identifying prolific types is to use offline profiling. In an offline run, a runtime system (type profiler 208) monitors memory allocation requests issued by an application 204, at step 402, and counts the number of objects of each type that are allocated on behalf of an application 204, at step 404. The type profile 304 is saved to a file, at step 406, for later use. When an application (or a JVM 112) exits, the collected type profile 304 is saved into a file. During an actual run, the runtime system uses a previously collected type profile 304 to perform various optimizations. Thus, no monitoring overhead is incurred during the production run of the application 204.

[0047] A disadvantage of this approach, as with any offline profiling method, is that it requires a separate profiling run and the type profiles 304 may vary depending on input data supplied to an application 204. In addition, an application 204 may consist of several execution phases with drastically different type profiles 304. A type profile 304 of such an application 204 is going to reflect its “average” behavior during the entire run. Although imperfect, this “one size fits all” approach still works quite well for many applications 204.

[0048] An adaptive approach, in contrast to the offline profiling approach, attempts to identify prolific types during the actual production run of the application 204. An obvious adaptive strategy would be to monitor each memory allocation in the application 204. However, this has the disadvantage of relatively high runtime overhead. It should be possible to reduce the overhead of monitoring object allocations by using sampling techniques.

[0049] An alternative approach is to monitor the garbage collections rather than memory allocations to identify prolific types. Most unreachable objects are expected to be of prolific types. Although examining unreachable objects could lead to a fairly accurate characterization of types as prolific or non-prolific, it would be an expensive operation. Again, sampling techniques using weak references, or other techniques, could help reduce the overhead, since only a small subset of the unreachable objects would then be examined.

[0050] The type-based memory allocator 202 partitions heap space 306 into a prolific space 308 and a non-prolific space 310: P-space and NP-space, respectively. Note that the actual allocation mechanism is related to the kind of collector used by the system. When used with a copying (type-based) collector 120, the memory allocator uses 202 different regions of the memory 124 for the P-space and NP-space. With a non-copying collector, the objects of prolific and non-prolific types are tagged differently, but not necessarily allocated in separate memory regions.

[0051] When we discuss prolific and non-prolific spaces, we do not necessarily mean two different regions of memory, e.g., of the heap. With a non-copying collector, for example, prolific and non-prolific objects may reside next to each other in memory. As will be obvious to those of ordinary skill in the art in view of the present discussion, a garbage collection system, according to a preferred embodiment of the present invention, could distinguish between prolific and non-prolific objects, such as by using a single bit in an object header or by looking at an object type and checking that type against a type profile.

[0052] Given an allocation request for an object of a certain type, the memory allocator 202 checks the type profile 304 of the application (with information about whether or not the type is prolific) to decide whether to place the object in the P-space 308 or NP-space 310. Hence, compared to a traditional memory allocator, the allocation path of the type-based memory allocator 202 would have an extra step for checking the type of the object. However, since the prolificacy of types is known at compile-time, the compiler 206 can avoid the overhead of the type check by simply calling (and possibly inlining) a specialized version of the allocator for prolific or non-prolific types. An alternative embodiment performs this optimization.

[0053] It should be noted that the compiler 206 is typical of many compilers used in object-oriented programming languages in that it may have several modes of operation, including:

[0054] Incremental compilation—during which time the compiler may compile only a program code segment, linking and loading any required modules. The program segment may include any portion of the program, up to and including the entire program code.

[0055] Recompilation of pre-compiled code—the compiler may recognize that a portion of needed code has been previously compiled and recompiles the code.

[0056] Traditional compilation—translates an entire program code.

[0057] Mixed-mode compilation—may perform a combination of any of the above modes.

[0058] The type-based garbage collector 210 assumes that most objects of prolific types die young, and performs minor collections only on the P-space 308. Because objects of prolific types account for most of heap space 306, a preferred embodiment the invention expects to collect enough garbage on each P-space 308 collection. A full collection of both P-space 308 and NP-space 310 may be induced by a variety of triggering events described in prior art. One such triggering event occurs when a P-space 308 collection does not yield a sufficient amount of free space. Because enough unreachable objects should be uncovered during a P-collection, the full collections are expected to be infrequent. Objects remain in their respective spaces after both P-space 308 and full collections—i.e., unlike generational collection, objects that survive a P-space 308 (minor) collection stay there and are not “promoted” to the NP-space 310. This enables the compiler 206 to eliminate unnecessary write barriers with a relatively simple type check, as described herein below. Given the low survival rates of objects in the P-space 308, the “pollution” of P-space due to longer-lived objects is not expected to be a significant problem.

[0059] In order to ensure that during a P-space 308 (minor) collection, any object reachable from an object in the NP-space 310 is not collected, garbage collection in accordance with a preferred embodiment of the invention has to keep track of all such pointers from an object in the NP-space 310 to an object in the P-space 308. This is accomplished by executing a write barrier code for pointer assignments during program execution, which records such references and places them in a write buffer 302. The contents of the write buffer 302 represent roots used in a P-space 308 collection.

[0060] The type-based scheme requires a write barrier to be executed only upon creation of a reference from the NP-region to the P-region. Write barriers may be executed in other cases but those executions of write barriers will unnecessarily reduce throughput of an application (i.e., useless overhead which can be optimized away). In other words, a write barrier has to be compiled into a code at a point in a program when said program creates a reference from a source object that is non-prolific to a target object that is prolific. In the presence of a class hierarchy (e.g., programs written in the Java programming language), a write barrier has to be compiled into a code when a source object may be non-prolific and a target object may be prolific.

[0061] A compiler can determine on-the-fly whether a write barrier is necessary for a program point when a reference is created and compile a write barrier into a code. If a compiler determines that a write barrier is not necessary for a program point when a reference is created, a write barrier code is not included. Alternatively, a compiler can first identify each place in a program when a write barrier may be necessary and then eliminate an unnecessary write barrier on-the-fly or in a post-processing step.

[0062] In the type-based collection, objects are not moved from P-space 308 to NP-space 310 or vice versa. Hence, write barriers (which are supposed to keep track of references from NP-space to P-space) can be eliminated at compile time based on a simple type check shown in FIG. 6. More specifically, given an assignment statement where the pointer of an object of type source is assigned a value corresponding to a pointer of an object of type target, the condition for eliminating a write barrier is expressed as code segment 702 in FIG. 7.

[0063] In an object-oriented language with polymorphism, such as Java, a code segment 702 requires analyses like class hierarchy analysis or rapid type analysis, similar to those needed for inlining or devirtualization of methods. This conservativeness is made explicit by redefining code segment 702 to be code segment 704. Given a declared type T of an object o, the compiler 206 checks for MustBeProlific(o) by checking that all children of T in the class hierarchy are prolific, and can similarly check for MustBeNonProlific(o).

[0064] Dynamic class loading is another feature of languages like Java that forces compile-time analysis to be done more conservatively. Again, the problem is similar to the problem with inlining of virtual methods in the presence of dynamic class loading. Due to dynamic class loading, a program can load a new class that is non-prolific but subclasses a prolific class, unless the prolific class is declared final. Note that with a type prolificacy based methodology, a newly loaded class (which the compiler does not know about) would not be classified as prolific, since no instance of that class would have been seen. Therefore, while the check MustBeNonProlific(target) in code segment 704 could be done by looking at the existing type hierarchy, the check MustBeProlific(source) would be conservatively set to IsFinalProlific(source), so that the code continues to work correctly after new classes are loaded. In this case, the condition under which a write barrier may be eliminated becomes code segment 706.

[0065] It is possible to use the techniques for inlining virtual methods in the presence of dynamic class loading, like preexistence analysis and extant analysis, to improve the effectiveness of code segment 706. For example, using extant analysis, if a specialized method in which the source reference is known to be extant (i.e., pointing to an existing object) is created, the test MustBeProlific(source) can be performed based on the existing class hierarchy, without worrying about any new classes that might be loaded. A much simpler technique, described below, is used in the preferred embodiment.

[0066] The prolific types are likely to be leaves, or close to leaves, in a type hierarchy. The intermediate classes are typically used for defining a functionality that is common to all of their children classes. The subclasses then refine the behavior of their parent classes and are usually instantiated more frequently than their respective parent classes. While it is possible that a prolific class may have one or more subclasses that are not prolific, all children of prolific types are treated as prolific. This greatly simplifies the test to check if a type is definitely prolific. The test returns true if the declared type of the variable is prolific, and returns false otherwise (without looking any further at the class hierarchy). In particular, code segment 708 for eliminating redundant write barriers can be done without worrying about any new classes that may be dynamically loaded in the future (because any dynamically loaded class that subclasses a prolific type are regarded as prolific).

[0067] There are various extensions to the basic scheme, which can improve the performance of the system. One of the fields in an object header usually points to a special object describing its type (or class) information. For example, in the Java Virtual Machine 112 of the present invention, this field points to a type information block (TIB) and is called a TIB field. Scanning TIB pointers for every reachable object does not seem to be necessary and can be avoided in the type-based scheme. It is sufficient for only one object of a type to survive a collection to ensure that the TIB of that object is scanned and marked as live. The scanning of TIB fields of all other instances of that type are unnecessary, although the garbage collector will realize after reaching the TIB object that it has already been marked. Since the number of distinct types is small, the number of objects representing them is also small. It follows that such objects can be classified as instances of a non-prolific type and placed in the NP space 310. As a result, the TIB fields (which now point to the NP-space 310) do not have to be scanned during a P-space 308 collection.

[0068] The idea of not scanning TIB objects during a P-space 308 collection can be taken further by observing that only objects of prolific types need to be scanned in the P-space 308 collection. In the type-based scheme of the invention, the number of pointers processed can be reduced even further during a P-space 308 collection.

[0069] During the P-space 308 scanning process, for each object, the garbage collector 120 requests the list of fields that are references. This list is created when a class is loaded. Normally, the returned list contains all such reference fields. Consequently, all such references are first processed and then some of them (e.g., those pointing to young objects) are scanned. However, in the type-based collector 120, there is no need to return a complete list of reference fields to the collector 120 during a P-space 308 collection. Only the references pointing to objects of prolific types have to be returned (because objects residing in the NP-space 310 are only scanned during a full collection). To support this extension, the collector is provided with two different sets of methods returning the lists of reference fields: one (returning a partial list) for a P-space 308 collection and one (returning a full list) for a full collection.

[0070] By defining several degrees of prolificacy of types, several P-spaces 308 can be created. Objects corresponding to different levels of prolificacy will have different lifetimes. Each such space may be collected with a different frequency. This is different from generational garbage collectors employing multiple generations and promoting objects with different ages to different generations.

[0071] It would be useful to have a separate sub-space within the NP-space 310 for objects of non-prolific types that cannot point to objects in the P-space 308 directly. By partitioning the NP-space 310 in this manner, the need to maintain card marking data structures for this sub-space can be eliminated because a write barrier cannot be executed on any object in this sub-space.

[0072] Combining type-based memory management with lifetime analysis of objects may lead to further performance improvements. Although, most short-lived objects are instances of prolific types, there may be some non-prolific types whose instances are always short lived. It may be advantageous to collocate such objects of non-prolific types with objects of prolific types in the P-space 308 (and to treat them as if they were instances of prolific types) thereby reducing the pollution of NP-space 310, albeit only slightly. However, if such short-lived objects can point directly to a P-space 308, then this collocation can also reduce the pollution of P-space 308 after a P-space 308 collection.

[0073] The type-based approach is therefore different from the generational approach in a number of ways:

[0074] It involves pre-tenuring objects of non-prolific types into the heap partition, which is collected less often. These objects do not need to be scanned during P-region (minor) collections. Those savings may be limited because instances of non-prolific types, by their very nature, would not have occupied a lot of space in the nursery.

[0075] Objects of prolific types are never promoted to the heap partition, which is collected less often. This can be a double-edged sword. If objects of prolific types live for a long time, they can pollute the P-region, causing the scanning time to increase during future minor collections (fortunately, it does not happen in practice). However, this approach can also help avoid the negative side effects of premature promotion of young objects that are going to die soon anyway (namely, executing more write barriers; dragging more objects via write buffers into the old generation; and requiring more major collections).

[0076] The separation between the heap partitions is based on static characteristics, i.e. the types of objects, rather than dynamic characteristics such as their ages. This allows unnecessary write barriers to be eliminated with a simple (and well-known in the context of dealing with virtual methods) compile-time analysis. This, apart from saving the direct overhead of executing write barriers, can also help avoid adding unnecessary objects to the write buffer, thus leading to fewer roots for minor collections, and potentially, more effective garbage collection.

[0077] During a P-region collection, only objects of prolific types have to be scanned. As a result, reference fields that can only point to objects of non-prolific types do not even need to be examined. Fewer pointers to be examined translates into shorter garbage collection pauses. This optimization is also a consequence of the type-based nature of the division. It is possible because in our scheme, the assignment of an object to a separate region of collection depends only on the prolificacy of its type. This optimization cannot be performed in a generational scheme in which a reference field can point to either the nursery or the mature space; because the direction of a pointer cannot be known without actually examining it, all reference fields have to be checked for pointers into the nursery.

[0078] The present invention can be realized in hardware, software, or a combination of hardware and software. A system according to a preferred embodiment of the present invention can be realized in a centralized fashion in one computer system, or in a distributed fashion where different elements are spread across several interconnected computer systems. Any kind of computer system—or other apparatus adapted for carrying out the methods described herein—is suited. A typical combination of hardware and software could be a general-purpose computer system with a computer program that, when being loaded and executed, controls the computer system such that it carries out the methods described herein.

[0079] The present invention can also be embedded in a computer program product, which comprises all the features enabling the implementation of the methods described herein, and which—when loaded in a computer system—is able to carry out these methods. Computer program means or computer program in the present context mean any expression, in any language, code or notation, of a set of instructions intended to cause a system having an information processing capability to perform a particular function either directly or after either or both of the following a) conversion to another language, code or, notation; and b) reproduction in a different material form.

[0080] Although specific embodiments of the invention have been disclosed, those having ordinary skill in the art will understand that changes can be made to the specific embodiments without departing from the spirit and scope of the invention. The scope of the invention is not to be restricted, therefore, to the specific embodiments, and it is intended that the appended claims cover any and all such applications, modifications, and embodiments within the scope of the present invention.

[0081] What is claimed is: 

1. A method of compiling program, the method comprising: determining that a program code, at a point in a program, creates a reference from a source object to a destination object; and associating write barrier code with the program code if, at the point in the program, the source object is non-prolific and the destination object is prolific, otherwise determining not to associate write barrier code with the program code.
 2. The method of claim 1, wherein the program executes pointer assignment from the source object to the destination object, and the source object being addressable through a first pointer and the destination object being addressable through a second pointer, and wherein the associating write barrier code with the program code comprises determining not to associate write barrier code with the program code if at least one of the following: the first pointer points to a source object whose type is prolific, and the second pointer points to an object whose type is non-prolific.
 3. The method of claim 1, wherein the program is written in an object-oriented language.
 4. The method of claim 1, wherein the program is written in a language that supports dynamic class loading.
 5. The method of claim 4, wherein all children of prolific type objects are treated as prolific types.
 6. A method of compiling program, the method comprising: including write barrier code with a compiled program code when at a point in a program the compiled program code is for executing a pointer assignment from a source object to a target object, and the source object is non-prolific and the target object is prolific, each source object being addressable through a first pointer and each target object being addressable through a second pointer; and determining not to include write barrier code with the compiled program code if the first pointer points to a source object whose type is prolific.
 7. The method of claim 6, further comprising: determining not to include write barrier code with the compiled program code if the second pointer points to a target object whose type is non-prolific.
 8. The method of claim 6, wherein the program segment is written in a language that supports dynamic class loading.
 9. The method of claim 6, wherein all children of prolific type objects are treated as prolific types.
 10. A method of compiling program, the program executing pointer assignments from a source object to a destination object, each source object being addressable through a first pointer and each destination object being addressable through a second pointer, the method comprising: determining not to associate write barrier code with a compiled program code if the second pointer points to a destination object whose type is non-prolific.
 11. The method of claim 10, further comprising: determining not to associate write barrier code with a compiled program code if the first pointer points to a source object whose type is prolific.
 12. The method of claim 10, wherein the program is written in an object-oriented language.
 13. The method of claim 10, wherein the program is written in a language that supports dynamic class loading.
 14. The method of claim 10, wherein all children of prolific type objects are treated as prolific types.
 15. A method of compiling program, the program executing pointer assignments from a source object to a destination object, each source object being addressable through a first pointer and each destination object being addressable through a second pointer, the method comprising: eliminating write barrier code from association with compiled program code when the first pointer points to a source object whose type is prolific.
 16. The method of claim 15, further comprising: eliminating write barrier code from association with compiled program code when the second pointer points to a destination object whose type is non-prolific.
 17. The method of claim 15, further comprising: associating write barrier code with compiled program code when the source object is non-prolific and the destination object is prolific.
 18. The method of claim 15, wherein the program is written in an object-oriented language.
 19. The method of claim 15, wherein the program is written in a language that supports dynamic class loading.
 20. The method of claim 15, wherein all children of prolific type objects are treated as prolific types.
 21. A computer system comprising: a first memory for storing a compiler; a second memory for storing a computer program, the computer program for executing pointer assignments from a source object to a destination object, each source object being addressable through a first pointer and each destination object being addressable through a second pointer; and a processor, communicatively coupled to the first memory and the second memory, for compiling the computer program and thereby including write barrier code with compiled program code when a source object is non-prolific and a destination object is prolific, and for determining not to include write barrier code with compiled program code when the first pointer points to a source object whose type is prolific, and for determining not to include write barrier code with compiled program code when the second pointer points to a destination object whose type is non-prolific.
 22. The computer system of claim 21, wherein the computer program stores objects in memory organized in a prolific space and a non-prolific space.
 23. A computer system comprising: a processor; a memory, communicatively coupled to the processor, for storing a computer program, the computer program for executing pointer assignments from a source object to a destination object, each source object being addressable through a first pointer and each destination object being addressable through a second pointer; and a compiler, communicatively coupled to the processor and the memory, for compiling the computer program and thereby determining whether to include write barrier code with compiled program code, and for determining not to include write barrier code with compiled program code when the first pointer points to a source object whose type is prolific.
 24. The computer system of claim 23, wherein the compiler further for determining not to include write barrier code with compiled program code when the second pointer points to a destination object whose type is non-prolific.
 25. The computer system of claim 23, wherein the compiler further for including write barrier code with compiled program code when a source object is non-prolific and a destination object is prolific.
 26. The computer system of claim 23, wherein the computer program is written in an object-oriented language.
 27. The computer system of claim 23, wherein the computer program stores objects in memory organized in a prolific space and a non-prolific space.
 28. A computer readable medium comprising computer instructions for compiling program, the computer instructions comprising instructions for: determining that a program code, at a point in a program, creates a reference from a source object to a destination object; and associating write barrier code with the program code if, at the point in the program, the source object is non-prolific and the destination object is prolific, otherwise determining not to associate write barrier code with the program code.
 29. The computer readable medium of claim 28, wherein the program executes pointer assignment from the source object to the destination object, and the source object being addressable through a first pointer and the destination object being addressable through a second pointer, and wherein the associating write barrier code with the program code comprises: determining not to associate write barrier code with the program code if at least one of the following: the first pointer points to a source object whose type is prolific, and the second pointer points to an object whose type is non-prolific.
 30. The computer readable medium of claim 28, wherein the program is written in an object-oriented language.
 31. The computer readable medium of claim 28, wherein the program segment is written in a language that supports dynamic class loading.
 32. The computer readable medium of claim 28, wherein all children of prolific type objects are treated as prolific types.
 33. A computer readable medium comprising computer instructions for compiling program, the computer instructions comprising instructions for: including write barrier code with a compiled program code when at a point in a program the compiled program code is for executing a pointer assignment from a source object to a target object, and the source object is non-prolific and the target object is prolific, each source object being addressable through a first pointer and each target object being addressable through a second pointer; and determining not to include write barrier code with the compiled program code if the first pointer points to a source object whose type is prolific.
 34. The computer readable medium of claim 33, further comprising instructions for: determining not to include write barrier code with the compiled program code if the second pointer points to a target object whose type is non-prolific.
 35. A computer readable medium comprising computer instructions for compiling program, the program executing pointer assignments from a source object to a destination object, each source object being addressable through a first pointer and each destination object being addressable through a second pointer, the computer instructions comprising instructions for: determining not to associate write barrier code with a compiled program code if the second pointer points to a destination object whose type is non-prolific.
 36. The computer readable medium of claim 35, further comprising instructions for: determining not to associate write barrier code with a compiled program code if the first pointer points to a source object whose type is non-prolific.
 37. A computer readable medium comprising computer instructions for compiling program, the program executing pointer assignments from a source object to a destination object, each source object being addressable through a first pointer and each destination object being addressable through a second pointer, the computer instructions comprising instructions for: eliminating write barrier code from association with compiled program code when the first pointer points to a source object whose type is prolific.
 38. The computer readable medium of claim 37, further comprising instructions for: eliminating write barrier code from association with compiled program code when the second pointer points to a destination object whose type is non-prolific.
 39. The computer readable medium of claim 37, further comprising instructions for: associating write barrier code with compiled program code when the source object is non-prolific and the destination object is prolific.
 40. The computer readable medium of claim 37, wherein the program is written in an object-oriented language.
 41. The computer readable medium of claim 37, wherein the program segment is written in a language that supports dynamic class loading.
 42. The computer readable medium of claim 37, wherein all children of prolific type objects are treated as prolific types. 